Ad-hoc user account creation

ABSTRACT

A mechanism that allows a user to easily configure a rules engine to apply rules to decide which requests for access to a user&#39;s computer resources are to be granted and which are denied. A trusted token, such as a certificate of identity issued by a trusted third party authority that verifies identities of computer users, is included in a calling card object provided by the requesting user to the (server) computer that controls the resources desired by the requester. Additional conditions for access may be specified as desired by the user of the server computer.

FIELD

The present invention relates broadly to computer networks.Specifically, the present invention relates to computers automaticallynegotiating a level of trust required before one computer serves assetsto another computer.

BACKGROUND

Proliferation of portable computers and computer networks hasdrastically widened the scope of computer usage for the average computeruser. Access to computer networks is now offered in such public venuesas coffee shops, hotels, and other places where people connect to anetwork in a casual or ad-hoe manner, for example, a one-time connectionor multiple connections over a brief period. However, establishingconnections between individual computers connected in this ad-hoc mannerhas not evolved with this expanded access. For online communication,individual users still must use third party resources, such as websitesthat host multiple users, to share resources or even to facilitatecommunication. In these conventional resource-sharing environments, auser must still establish an account through a largely mechanicalprocess on the client end, where a user approaches a website by firstasking for an account to be created, and then engaging in a dialoguewhere the user either supplies a username and password, or is assignedthe username and password from the server asked to create an account.

As computing power has evolved, even the simplest of computers soldtoday can function as servers and distribute computing resources andassets to other computers. However, the average computer user has noeasy way to validate the identity of another user requesting access, andad-hoc user account creation suffers a serious shortcoming from theperspective of security. There also is no simple way for one computer toshare resources unless either a third party entity is involved, or thecomputer users manually share resources. Most computer users are notinterested in performing manual account creation for everyone who wantsaccess to his or her computer resources. Also, varying levels ofscrutiny to access requests currently are insufficient for the averageuser. Where an individual user may not require a high level of scrutinyfor someone wishing to access a collection of stored computer images orphotographs, a higher degree of security may be desired for moresensitive information that a computer user may only wish to share withselect individuals.

Thus there remains a significant need for a mechanism for computer usersthat provides security and automation in a resource-sharing environmentthat is easily configured by a user.

SUMMARY

The present invention solves the problems described above by providing amechanism that allows a user to easily configure a rules engine thatapplies rules to decide which requests for access to a user's computerresources are to be granted and which are denied. In an embodiment, atrusted token, such as a certificate of identity issued by a trustedthird party authority that verifies identities of computer users, can beincluded as part of an electronic calling card provided by therequesting user to the (server) computer that controls the resourcesdesired by the requester. Additional conditions for access may bespecified as desired by the user of the server computer.

In one aspect, the present invention provides a method for a firstcomputer to access a second computer, by establishing a connectionbetween a first and second computer and passing from the first computerto the second computer a trusted token indicating an identity of a user.The second computer then establishes an identity-based account based onthe trusted token received from the first computer. In an embodiment,the trusted token is a token issued by an identity-verificationauthority, and identifies the user by name. In an embodiment, thetrusted token is an electronic certificate issued by anidentity-verification authority and includes an encrypted key and auser-configurable portion containing information provided by the user.The identity-based account is established in a manner characterized byan absence of interaction between the second computer and a user of thefirst computer. Once trust is established between the first computer andthe second computer, the second computer fulfills resource requests madeby the first computer.

In another aspect, the present invention provides a computer-readablemedium containing instructions which, when executed by a computer,engage a first computer in communication with a second computer, byreceiving a resource request from a first computer over a computernetwork; engaging a rules engine to apply a set of criteria to therequest received from the first computer; denying the resource requestif a criterion in the set is not satisfied; receiving a trusted tokenfrom the first computer; engaging an identity verification module toread a trusted token received from the first computer; establishing anidentity based on the trusted token; and fulfilling the resource requestreceived from the first computer.

In yet another aspect, the present invention provides an interface thatallows a user to specify rules to be applied by a rules engine inevaluating a request for access made when the user of another computerinitiates contact by sending a calling card having a digital certificateindicating the human identity of the user as well as other informationthat can be evaluated by a rules engine to determine whether or not togrant access to the requesting user. The interface also allows a user tospecify rules that determine what information is provided on the callingcard presented to other computers.

Many other features and advantages of the present invention will berealized upon reading the following detailed description, whenconsidered in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network environment of computers in which thepresent invention is implemented.

FIG. 2 illustrates major functional components used in variousembodiments of the present invention.

FIG. 3 illustrate user interface components that allow a user to manageand edit conditions that are applied by a rules engine to incomingcalling cards as well as manage and edit conditions that determine whatinformation is displayed on a calling card.

FIG. 4 illustrates communication between a client (requesting device)and server in embodiments of the present invention.

FIG. 5 and illustrates the flow of a sequence of acts performed by theserver of FIG. 4.

DETAILED DESCRIPTION

Directing attention to FIG. 1, there is shown network environment 100 inwhich a plurality of computers 102-1 through 102-n are connected. In thepreferred embodiment, environment 100 is a local area network maintainedby a server computer (not shown) having control over individualconnections to network 100, and possibly providing access toremotely-located computers and/or networks. It is contemplated thatnetwork 100 allows users to connect with very little or no scrutiny atall, so that each user of computers 102 is responsible for his or herdesired security level.

In addition to hardware and software components found on conventionalcomputers such as desktop computers, and portable computers such aslaptops, palmtops, and the like, computer 102 incorporates thefunctional modules shown in FIG. 2. Rules engine 104 manages accessgranted to requesting users by applying one, some, or all conditionsspecified by the user of computer 102 to an electronic calling card thataccompanies a received request. In an embodiment, verification module106 is invoked to inspect and verify identity indicia contained in thecalling cards. In an embodiment, the identification indication is issuedby a third party that is an authority that confirms user identity andissues a trustable indication of the user's identity. However, such anidentification indication can also be verified through a variety ofmethods, such as public key/private key schemes such as employed byKerberos systems. Verification module 106 can be invoked by rules engine104 to verify an identity key supplied by a user in an electroniccalling card that the user sends to computer 102 to request access. Inan alternative embodiment, verification module 106 can review thereceived calling card and invoke rules engine 104 to determine ifconditions for access are present in the calling card. In embodiment,key distribution center 105 accommodates verification modules 106resource requests to assist in authenticating the user associated withthe calling card.

Computer 102 also includes database 108, which can be used for trackingaccess requests as well as accounts created for requesting entities.Directing attention to FIG. 3, user interface 110 is a module thatallows the user to configure varying combinations of conditions that arechecked in incoming calling cards. In an embodiment, interface 110 alsoallows the user to create and edit his or her calling card, by insertingan identity indicia and/or information items that serve as conditionsfor establishing an account and gaining access to resources on anothercomputer. Interface 110 is divided into two functional interfaces.Incoming introduction interface 112 relates to a user-configurable setof controls, or policies that are applied by rules engine 104 toincoming introductions. Calling card configuration interface 114 allowsthe user to configure a set of controls, conditions or policies that areapplied by rules engine 104 to the calling card the user will present inintroductions to server 104.

As illustrated, interface 110 comprises a representation of individualobjects having various embodiments. For example, object 116 contains anon/off toggle 118, a condition description 120, and reference value 122.On/off toggle 118 simply makes the object available to rules engine 104.Condition display 120 includes some indicia that inform a user of thenature of the condition. Many different indicia are possible. Forexample, a written description may be used in one embodiment, an imagein another embodiment, animated graphics displayed in anotherembodiment, etc. Reference value 122 contains references to additionalrules on object 116 as desired by the user. As illustrated in FIG. 3,and considering interface 110 to include a plurality of templates 110 a,110 b, 110 c, etc, additional versions of interface 110 can be organizedin sequence to allow rule engine 104 to execute a sequence of rules anddisplay the sequence of rules displayed over a sequence of templates(referenced in reference value 122 as belonging to templates 110 b and110 c). In some cases the sequence of rule application and can occurover time periods specified by the user, or by events triggered by arules engine belonging to the contacted machine, to the same conditiondescribed in condition display 120 on templates 110 b and 110 c.

As described above, object 116 can be used for a wide variety ofconditions, rules, and the like to be used by rules engine 104 todetermine whether or not to grant access and/or resources to the senderof the calling card, or to simply determine whether or not to add theidentity of the calling card's presenter to a trusted identity database.In is contemplated that frequency of contact initiation be representedby object 116, so that a user can configure rules engine 104 to onlyallow a desired number of contacts to be evaluated over a time period.

Similarly, interface 114 includes object 126, with similar features asobject 126, and may also be implemented over interface templates 114 a,114 b, 114 c, etc. Both interface 112 and 114 can be displayedsimultaneously to a user as illustrated in FIG. 3, but can also appearseparately if a user closes display of either interface 112 or 114. Inan embodiment, it is contemplated that interface 112 and 114 are incommunication with a rules database containing rules that are selectedfor use by the user of interface 110 and passed to rules engine 104

Explanation of operation of an introduction is made with reference toFIG. 4. Client 400 initiates contact with server 402 over acommunication link belonging to network 404. Both client 400 and server402 are user machines that maintain rules engines and interfaces similarto interface 110 described above. Client 400 transmits the calling carddescribed above to server 402. In some cases, client 400 transmits thecalling card only after issuing a resource request to server 402, whichresponds with a denial of the request. Upon sending a denial of theresource request, in embodiments where rule engine 104 operates as abackground object, server 402 may initiate preparation of a rules enginesimilar to rules engine 104, by optimizing processing resources andreserving processor resources to apply rules engine 104 withoutsuffering any performance degradation noticeable to a user. When server402 receives a calling card from client 400, in an embodiment, thecalling card received is examined for conditions as well as a digitalcertificate. Rules engine 104 can then apply authentication measures tothe digital certificate, or the public key and or/private key thataccompany the digital certificate. In an embodiment, rules engine 104can pass the digital certificate to a separate authentication module(not illustrated) for separate processing. In embodiments where server402 operates in a Kerberos environment, authentication proceeds in adomain controlled by key distribution center 105.

Depending on the evaluation of rules applied by rules engine 104, server402 may create an identity for the user associated with client 400 andadd this identity to a trusted identity database maintained by server404. In an embodiment, server 402 harvests other information besidesidentity from client 400, which can be added to the identity database orassociated with a log of failed access attempts, thus forming ablacklist of clients to be denied access in future instances of contact.It is contemplated that besides identity information, information suchas time of the contact, the location of the contact, such as on whatpart of a network or what network if the user of server 404 connects todifferent networks. It is contemplated that a typical scenario fordenial of client 400 to occur if client 400 presents a calling cardbearing a bogus certificate. Besides interfacing with key distributioncenter 105, server 404 can also perform message integrity checksdirectly on the certificate and/or other parts of the received callingcard.

It is contemplated that a calling card presented by client 400, inaccordance with the present invention, be of the same general format ororganization of a calling card that client 400 would able to receive.However, in alternative embodiments, calling cards can be madearbitrarily complex, depending on user needs. For example, differentmedia assets could be presented in a calling card as part of a dialoguebetween a presentation object residing on the calling card and server402. For example, if server 402 employs a rules engine that initiallyrejects the calling card presented by client 400, the rules enginemaintained on client 400 may generate an updated calling card andpresent it to server 402 with additional information that might resultin server 402 fulfilling a resource or access request made by client400.

Directing attention to FIG. 5, a sequence of acts is executed by acomputer in accordance with the present invention. Beginning at act 500,a connection is established between client 400 and server 402. At act502, server 402 receives a resource request in the form of a callingcard presented by the user of client 400. As explained above, thepresentation of the calling card can be triggered by server 402'srejection of an earlier resource request made by client 400. At act 504,server 402 reads the calling card, and extracts whatever information asdesignated by rules engine 104 located on server 402. Rules engine 104is then applied to this extracted information at act 506, includingidentity information provided in a trusted token issued by an identityverification authority. Act decision step 508, a determination is madeas to whether conditions for access are satisfied. If yes, anidentity-based account is created on server 402 on behalf of the user ofclient 400. This account establishment can be reported (act 512) toother entities outside server 402, as well housekeeping or auditingprograms running on server 402. Finally, at act 514, access is grantedto client 400, and requested resources are allocated to client 400.Returning to decision step 508, if conditions for access are notsatisfied (based on evaluation by rules engine 104), server 402 logs theunsuccessful access attempt at act 516. Unsuccessful access attempts canbe evaluated by rules engine 104 in future contacts initiated by client402.

While a method and apparatus for ad-hoc user account creation has beenillustrated and described in detail, it is to be understood that manymodifications can be made to the various embodiments of the presentinvention without departing from the spirit thereof.

1-22. (canceled)
 23. A method for a first computerized apparatus tocontrol access to resources by a second computerized apparatus, themethod comprising: receiving a resource request from the secondcomputerized apparatus, the resource request at least comprising atrusted token from the second computerized apparatus, the trusted tokencontaining identity data of a user of the first computerized apparatus;determining when the request is authorized to access at least therequested resource; and creating an ad-hoc user account configured toaccess the requested resource upon a determination of authorized access,the ad-hoc user account comprising at least the identity data; whereinthe ad-hoc user account creation is characterized by automatic creationin response to the resource request.
 24. The method of claim 23, whereinthe trusted token comprises a token issued by an identity-verificationauthority.
 25. The method of claim 23, wherein the trusted tokenidentifies the user by name.
 26. The method of claim 23, wherein theresource request further comprises a calling card, the calling cardcomprising information configurable by the user.
 27. The method of claim23, wherein the user account is part of a user-account databaseconfigured to track access to the requested resource.
 28. The method ofclaim 23, wherein the resource request further comprises a calling card,and the determining comprises: extracting information from the callingcard as determined by a rules engine of the first computerizedapparatus; and applying one or more conditions of the rules engine onthe extracted information as part of said determining.
 29. The method ofclaim 23, wherein an authentication of the trusted token is performedprior to the creation of the ad-hoc user account.
 30. A computerizedapparatus, comprising: a network interface; a processor in datacommunication with the network interface; and a storage apparatus indata communication with the processor, the storage apparatus having aplurality of instructions stored thereon which are configured to, whenexecuted by the processor: generate a data structure comprising at leasta trusted token containing identity information of a user of theapparatus, the data structure generated via a rules engine configuredaccording to one or more criteria; establish a connection to a remotecomputerized apparatus using the network interface; transmit a requestvia the connection to access at least one resource managed by the remotecomputerized apparatus, the request comprising at least the datastructure; and access the at least one resource, where the at least oneresource is accessed based on an establishment of an ad-hoe user accountcomprising at least the identity information, the ad-hoc user accountcreation is characterized by automatic creation in response to therequest to access the at least one resource; wherein the transmitteddata structure is configured to enable the establishment of the ad-hocuser account upon authentication of the trusted token.
 31. Thecomputerized apparatus of claim 30, wherein at least a portion of theone or more criteria of the rules engine are configurable by the user.32. The computerized apparatus of claim 30, wherein the trusted tokencomprises an electronic certificate issued by an identity-verificationauthority.
 33. The computerized apparatus of claim 32, wherein theidentity-verification authority is a third-party.
 34. The computerizedapparatus of claim 30, wherein the generation of the data structure istriggered by a previously denied request to the at least one resource.35. The computerized apparatus of claim 30, wherein portions of the datastructure are configured to be editable by the user.
 36. Thecomputerized apparatus of claim 30, further comprising instructionsconfigured to, when executed, cause display to the user at least one ofthe one or more criteria prior to the generation of the data structure.37. A computer-readable apparatus comprising a non-transitory storagemedium, the storage medium comprising a plurality of executableinstructions configured to, when executed: receive a resource requestfrom a first computerized apparatus, the resource request comprising atleast a user identifier and a digital certificate; apply one or moreaccess criteria against the request to determine an authorization toaccess the requested resource; and create an ad-hoc user account toenable access to the requested resource upon a determination that therequest is authorized, the ad-hoc user account containing at least theuser identifier; wherein the ad-hoc user account creation ischaracterized by automatic creation in response to the resource requestwithout requiring additional user interaction.
 38. The apparatus ofclaim 37, wherein the digital certificate comprises a token issued by athird-party entity.
 39. The apparatus of claim 37, wherein at least oneof the one or more access criteria are configurable by a user.
 40. Theapparatus of claim 39, wherein at least one of the one or more accesscriteria comprises a frequency of contact initiation condition.
 41. Theapparatus of claim 37, wherein the account is part of an accessmanagement database is further configured to track access to therequested resource.
 42. The apparatus of claim 37, wherein anauthentication of the digital certificate is performed prior to thecreation of the ad-hoc user account.